Release 10.1A: OpenEdge Development:
Progress Dynamics Web Development Guide

Using custom images

You can add your own custom images for use by Progress Dynamics Web applications, and you can substitute different images for the default images installed with OpenEdge Studio. The recommended method for using custom images is to create one or more separate directories and set the value of the image_path session property to point to the appropriate directory.

The image_path property functions as a search path. It has the following format:

ry/img,..new_image_dir

where new_image_dir is the path (expressed relative to ry/img) to the directory containing the images to be displayed in your application. (Note that the location of ry/img can be either in your Web server’s document directory or in your OpenEdge installation area, depending on how the Web server is configured. See the "Configuring your Web server" section for more information.)

The default value of image_path is ry/img,..img, which resolves to ry/img itself. To use different images, store them in a separate subdirectory of ry (that is, a peer of the img directory), and specify that directory in image_path. For example, you might create the directory ry/web_img and set the value of the image_path property to:

ry/img,..web_img

To set the value of the property, use the Session Type Control tool as explained in the "ICFWS session" section.

You might want to use multiple directories as an organizing device. In that case, you can extend the value of image_path by adding more ry/img,...new_image_dir pairs, using a comma as the delimiter. For example:

ry/img,..web_img1, ry/img,..web_img2, ry/img,..web_img3

When the application code specifies an image, Progress Dynamics searches the alternate directories listed in the image_path property in the order in which they appear, until it finds the file. Thus, in the preceding example, suppose the application code refers to the file new_order.gif, which resides in the directory web_img2. Progress Dynamics searches first in web_img1 and then in web_img2, where it locates the file; web_img3 is not searched.